no desktop; kinit: name_to_dev_t (/dev/sda6) =sda(8,6)

[peter b]

- intrepid 810 beta, amd64 alternate install,
- foxconn A7GM-S MB with CrossFire enabled display --> 3200 integrated and 3450 on pciex16 slot
- install ok on /dev/sda7; weired network interface not detected --> installed without network
- grub installed --> PLS NOTE ON (hd0,6) - SPECIFIED AT INSTALL- NOT /dev/sda7
- at first boot, grub boot menu displayed and normal boot chosen --> the loading bullet was running and filled the load bar then
- entered the console display and messages appeared as follows

Loading, please wait ....
19+0 records in
19+ 0 records out
kinit: name_to_dev_t (/dev/sda6) =sda6(8,6)
kinit: trying to resume from /dev/sda6
kinit: No resume image, doing normal boot ....

ubuntu ; login

- In recovery mode I tried fixing x, checking fs --> did not help, same situation

- the question is - why sda6 and not sda7 ? in my case sda6 is the swap partition. any ideas ?

regards,
peter b

[peter b (b1pete)]

- menu.lst file pertinent info

## kopt_2_6_8=root=/dev/hdc1 ro
## kopt_2_6_8_2_686=root=/dev/hdc2 ro
# kopt=root=UUID=1383f714-b92b-4bf1-9bd2-8d851879f894 ro

## e.g. groot=(hd0,0)
# groot=(hd0,6)

and

title Ubuntu intrepid (development branch), kernel 2.6.27-4-generic
root (hd0,6)
kernel /boot/vmlinuz-2.6.27-4-generic root=UUID=1383f714-b92b-4bf1-9bd2-8d851879f894 ro quiet splash
initrd /boot/initrd.img-2.6.27-4-generic
quiet

title Ubuntu intrepid (development branch), kernel 2.6.27-4-generic (recovery mode)
root (hd0,6)
kernel /boot/vmlinuz-2.6.27-4-generic root=UUID=1383f714-b92b-4bf1-9bd2-8d851879f894 ro single
initrd /boot/initrd.img-2.6.27-4-generic

title Ubuntu intrepid (development branch), kernel Last successful boot
root (hd0,6)
kernel /boot/last-good-boot/vmlinuz root=UUID=1383f714-b92b-4bf1-9bd2-8d851879f894 ro quiet splash last-good-boot
initrd /boot/last-good-boot/initrd.img
quiet

title Ubuntu intrepid (development branch), memtest86+
root (hd0,6)
kernel /boot/memtest86+.bin
quiet

regards,
peter.

[peter b (b1pete)]

some more/additional info re hardware

lspci
00:00.0 Host bridge: Advanced Micro Devices [AMD] RS780 Host Bridge
00:01.0 PCI bridge: Advanced Micro Devices [AMD] RS780 PCI to PCI bridge (int gfx)
00:02.0 PCI bridge: Advanced Micro Devices [AMD] RS780 PCI to PCI bridge (ext gfx port 0)
00:09.0 PCI bridge: Advanced Micro Devices [AMD] RS780 PCI to PCI bridge (PCIE port 4)
00:11.0 SATA controller: ATI Technologies Inc SB700/SB800 SATA Controller [IDE mode]
00:12.0 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller
00:12.1 USB Controller: ATI Technologies Inc SB700 USB OHCI1 Controller
00:12.2 USB Controller: ATI Technologies Inc SB700/SB800 USB EHCI Controller
00:13.0 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller
00:13.1 USB Controller: ATI Technologies Inc SB700 USB OHCI1 Controller
00:13.2 USB Controller: ATI Technologies Inc SB700/SB800 USB EHCI Controller
00:14.0 SMBus: ATI Technologies Inc SBx00 SMBus Controller (rev 3a)
00:14.1 IDE interface: ATI Technologies Inc SB700/SB800 IDE Controller
00:14.2 Audio device: ATI Technologies Inc SBx00 Azalia (Intel HDA)
00:14.3 ISA bridge: ATI Technologies Inc SB700/SB800 LPC host controller
00:14.4 PCI bridge: ATI Technologies Inc SBx00 PCI to PCI Bridge
00:14.5 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI2 Controller
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
01:05.0 VGA compatible controller: ATI Technologies Inc Radeon HD 3200 Graphics
01:05.1 Audio device: ATI Technologies Inc RS780 Azalia controller
02:00.0 VGA compatible controller: ATI Technologies Inc Mobilitiy Radeon HD 3450
02:00.1 Audio device: ATI Technologies Inc RV620 Audio device [Radeon HD 34xx Series]
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 01)
04:05.0 FireWire (IEEE 1394): Texas Instruments TSB43AB23 IEEE-1394a-2000 Controller (PHY/Link)

lsusb
Bus 006 Device 002: ID 0ace:1215 ZyDAS WLA-54L WiFi
Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 004: ID 0bda:0111 Realtek Semiconductor Corp. Card Reader
Bus 005 Device 002: ID 1307:0165 Transcend Information, Inc.
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 004: ID 06bd:208f AGFA-Gevaert NV SnapScan e50
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

lshw -C network
  *-network
       description: Ethernet interface
       product: RTL8111/8168B PCI Express Gigabit Ethernet controller
       vendor: Realtek Semiconductor Co., Ltd.
       physical id: 0
       bus info: pci@0000:03:00.0
       logical ...

[Vinod (vinod-kurup)]

I had the same problem. I didn't keep track of exactly what I did, but it seems to be fixed.

I redid my swap like you did. I then restarted and booted into single user mode from grub. From the single-user menu, I did the reconfigure-broken-packages option and the fix-xorg option and now things seem to work. Sorry for not documenting my steps better...

[peter b (b1pete)]

thanks Vinod.

it is a 'wall' that in my case is v hard to penetrate so to speak - there are quite a few issues that make me think about

- the wired network is not detected ? hardy did a magnificent job, - why not intrepid ?
- kinit issue - why when reconfiguring swap its size is decreased by 4KB than what the fully functional hardy reports ?
- xorg.conf issue - why when using vesa driver on xorg.conf there is still no desktop ? isn't it supposed to be fail safe ? my hardware supports it.
- on the same x issue - why did hardy have no problems configuring it correctly and intrepid apparently fails on this account?

there are too many unanswered questions, each and every one have the potential to disrupt the desktop being functional. for sure there is a bug hidden somewhere in the code that comes to life on my hardware setup - and here again the question comes up, why did hardy install with no problems on the same hardware ? I'm writing this in hardy; never had a problem with it since april install. I'll wait and see what the full release brings about.

peter b

[Vinod (vinod-kurup)]

Hi Peter,

I agree with you. I wanted to get the 2.6.27 kernel for a specific fix
which allowed me to use my laptop unplugged. So I thought I'd be
adventerous and try the beta release. Big mistake so far.

Hopefully things will be cleaned up soon.

Best wishes,

Vinod

On Fri, Oct 3, 2008 at 10:45 PM, peter b <email address hidden> wrote:
> thanks Vinod.
>
> it is a 'wall' that in my case is v hard to penetrate so to speak -
> there are quite a few issues that make me think about
>
> - the wired network is not detected ? hardy did a magnificent job, - why not intrepid ?
> - kinit issue - why when reconfiguring swap its size is decreased by 4KB than what the fully functional hardy reports ?
> - xorg.conf issue - why when using vesa driver on xorg.conf there is still no desktop ? isn't it supposed to be fail safe ? my hardware supports it.
> - on the same x issue - why did hardy have no problems configuring it correctly and intrepid apparently fails on this account?
>
> there are too many unanswered questions, each and every one have the
> potential to disrupt the desktop being functional. for sure there is a
> bug hidden somewhere in the code that comes to life on my hardware setup
> - and here again the question comes up, why did hardy install with no
> problems on the same hardware ? I'm writing this in hardy; never had a
> problem with it since april install. I'll wait and see what the full
> release brings about.
>
> peter b
>
> --
> no desktop; kinit: name_to_dev_t (/dev/sda6) =sda(8,6)
> https://bugs.launchpad.net/bugs/277411
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Vinod Kurup, MD
<email address hidden>
http://kurup.org

[Vinod (vinod-kurup)]

oops... meant that as a personal reply to Peter.

[peter b (b1pete)]

for all interested with same hardware

- x is not able/smart (so far) to use CrossFire enabled BIOS setting; that is it can not BIND to ANY screens in spite of the fact when an attempt is made to start it, it lists all interfaces - internal and PCIe - but then it comes down with 'no screens found, giving up' message.

- so, to get a desktop in intrepid on this hardware, THE CROSSFIRE setting in BIOS MUST be set to DISABLE then x binds itself to the PCIe interface (graphic adapter).

- it is v interesting though, HARDY can live v happily with the above BIOS setting enabled.

regards,
peter b

[Dan Trevino (dantrevino)]

 Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

[peter b (b1pete)]

after the 810 full release it appears that the problem was solved on this account.

I can install (and installed) 810 with no glitches and work with it except no BIOS enabled crossfire. I don't mind about that

and now ....

.... a new issue popped up as reported on 320746. and again, it appears, is about having good response on hardy - the pcmcia mentioned on the 320746 WAS recognized immediately; it works fine on an acer laptop ; why not in intrepid?

still investigating why dynex pcmcia works fine on hardy but not on intrepid; I'll report results on 320746.

peter b

[Dan Trevino (dantrevino)]

Thank you Peter B.

This bug report is being closed due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status . Thank you again for taking the time to report this bug and helping to make Ubuntu better. Feel free to submit any future bugs you may find.