home bbs files messages ]

Forums before death by AOL, social media and spammers... "We can't have nice things"

   linux.debian.kernel      Debian kernel discussions      2,884 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 1,098 of 2,884   
   Daniel to All   
   Bug#1117256: linux-image-6.12.48+deb13-a   
   22 Oct 25 00:10:01   
   
   XPost: linux.debian.bugs.dist   
   From: ganchya@gmail.com   
      
   Hi,   
      
   I think that I have a similar problem. I have a thinkpad X1 with a docking   
   station.   
      
   With Bookworm I was able to connect external USB hard drives to the docking   
   station. Now with Trixie the hard drives are not detected when the docking   
   station is connected to the laptop. Even if the hard drives are connected   
   directly to the laptop.   
      
   If I disconnect the docking station the hard drives are detected.   
      
   Thanks,   
   Daniel   
      
   On Sun, Oct 12, 2025 at 7:57 PM Salvatore Bonaccorso    
   wrote:   
      
   > Control: tags -1 + moreinfo   
   >   
   > Hi Florian,   
   >   
   > On Sun, Oct 05, 2025 at 02:23:15PM +0200, Florian Hars wrote:   
   > > Package: src:linux   
   > > Version: 6.12.48-1   
   > > Severity: normal   
   > >   
   > > Dear Maintainer,   
   > >   
   > > when booting connected to a Dell WD19D docking station, my laptop can no   
   > longer activate   
   > > the ethernet interface of the docking station. If I then unplug the   
   > laptop from the   
   > > docking station, connect another laptop running Windows 11 to the   
   > docking station, wait,   
   > > until it has enummerated all devices, unplug and then replug the laptop   
   > running debian,   
   > > the network is detected and works (I am using it to send this report).   
   > >   
   > > The kernel log below misses the important bits, this is waht happened   
   > durin initial boot:   
   >   
   > Thanks. With "no longer activate the ethernet interface" I assume this   
   > means you can identify an earlier kernel revision which did not cause   
   > the problem?   
   >   
   > Two questions:   
   >   
   > First please try to boot with the most current version available in   
   > Debian unstable (6.16.11-1 right now), to see if the problem persist.   
   >   
   > Secondly if you are able to pinpoint a range where the kernel   
   > regressed, it would be great if you can bisect the changes between   
   > those versions (if you need instructions let us know).   
   >   
   > Regards,   
   > Salvatore   
   >   
   >   
      
   
Hi,

I think that I have a similar problem. I       have a thinkpad X1 with a docking station.

With       Bookworm I was able to connect external USB hard drives to the docking       station. Now with Trixie the        hard drives are not detected when the docking station is connected to the       laptop. Even if the hard drives are connected directly to the la       top.

If I disconnect the docking station the hard       drives are detected.

Thanks,
Daniel

On Sun, Oct 12, 2025 at 7:57 PM Salvatore       Bonaccorso <Control: tags -1       + moreinfo
       
       Hi Florian,
       
       On Sun, Oct 05, 2025 at 02:23:15PM +0200, Florian Hars wrote:
       > Package: src:linux
       > Version: 6.12.48-1
       > Severity: normal
       >
       > Dear Maintainer,
       >
       > when booting connected to a Dell WD19D docking station, my laptop can no       longer activate
       > the ethernet interface of the docking station. If I then unplug the       laptop from the
       > docking station, connect another laptop running Windows 11 to the docking       station, wait,
       > until it has enummerated all devices, unplug and then replug the laptop       running debian,
       > the network is detected and works (I am using it to send this report).
       >
       > The kernel log below misses the important bits, this is waht happened       durin initial boot:
       
       Thanks. With "no longer activate the ethernet interface" I assume       this
       means you can identify an earlier kernel revision which did not cause
       the problem?
       
       Two questions:
       
       First please try to boot with the most current version available in
       Debian unstable (6.16.11-1 right now), to see if the problem persist.
       
       Secondly if you are able to pinpoint a range where the kernel
       regressed, it would be great if you can bisect the changes between
       those versions (if you need instructions let us know).
       
       Regards,
       Salvatore
       
       
              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca